Repository navigation
chore(release): prepare v0.20.3 - #2827
Merged
Merged
Conversation
Review verdict: no findings — release prep looks correctPatch release v0.20.3, version/changelog only. Safe to merge assuming the publish-readiness checks in the description are accurate (not re-runnable from this review shell). Findings: none (no P0/P1/P2). What I checked beyond the diff:
Not reviewed: did not re-run |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | 2640f1f | Commit Preview URL Branch Preview URL |
Nov 04 2026, 08:51 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Михайло · project thread
What changed
Patch release v0.20.3 (20 PRs since v0.20.2). Version bumped across workspace, path-dep pins, npm packages,
Cargo.lock, auxiliary lockfiles (fuzz, hyperlight) and doc snippets; CHANGELOG entry added.Highlights:
markkit/fetchkitbuiltins (opt-in features), on markkit 0.3.1 / fetchkit 0.7.1 for RUSTSEC-2026-0436 (feat(builtins): add markkit and fetchkit builtins with the upstream CLI #2803, fix(deps): bump markkit to 0.3.1 and fetchkit to 0.7.1 for RUSTSEC-2026-0436 (calamine) #2823)Execution::output_fileand Deep Agents native output offload (feat: tee execution output to a VFS file; native capture offload for Deep Agents #2818)Why
User-requested patch release.
Before / After
Publish-readiness report:
cargo publish --dry-run -p bashkit-cpython-wasm -p bashkit -p bashkit-cli -p bashkit-scripted-tool: all four packaged and verified (exit 0)bashkit-cpython-wasm-0.20.3.crate: 8,159,915 bytes (< 10 MiB)@everruns/bashkit,@everruns/bashkit-wasm); 0.20.3 is greatercargo metadata --lockedpasses for fuzz, hyperlight, hyperlight/hostcheck_doc_links.py: OK;check_workflow_parity.py: OK;cargo fmt --check: OKjust apidocs: no drift (Python and TypeScript)Risk
releaseenvironment is missing,publish.ymlfails and needs a re-run after fixing config.Checklist